Path: ...!3.us.feeder.erje.net!1.us.feeder.erje.net!feeder.erje.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!feeder.cambriumusenet.nl!feed.tweaknews.nl!posting.tweaknews.nl!fx13.ams1.POSTED!not-for-mail From: NONONOmisc07@fmguy.com Newsgroups: alt.usenet.offline-reader.forte-agent,alt.comp.os.windows-10 Subject: Re: Two different computers; Forte-Agent 1.93 does nothing when I click on it, Message-ID: <8vbtei9acrt9hqfl0prne6bfi7rgrqcp28@4ax.com> References: <8i5ieiphhc106tldr4g69n59pnp9sp8pno@4ax.com> X-Newsreader: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Antivirus: AVG (VPS 230829-4, 8/29/2023), Outbound message X-Antivirus-Status: Clean Lines: 117 X-Complaints-To: abuse@tweaknews.nl NNTP-Posting-Date: Wed, 30 Aug 2023 02:56:49 UTC Organization: Tweaknews Bytes: 6156 Date: Tue, 29 Aug 2023 22:56:45 -0400 X-Received-Bytes: 5882 X-Original-Bytes: 5695 On Sat, 26 Aug 2023 09:00:00 +1200, Ralph Fox <-rf-nz-@-.invalid> wrote: >On Fri, 25 Aug 2023 03:12:53 -0400, Paul wrote: >> On 8/25/2023 1:02 AM, Micky wrote: >>> >>> Win10, fully updated, one Pro and one Homet >>> >>> Agent worked fine until recently and two nights ago, but they stopped. >>> >>> >>> About 2 weeks ago, it wouldn't even start. I'd click and if I clicked >>> on the icon the desktop the little blue circle would be there for a few >>> seconds. If I clicked where it's pinned to the taskbar nothing at all >>> happened. >>> >>> Event Viewer calls it an Event 1001, but it calls a lot of things that. >>> Level 4, APPCRASH >>> >>> Continuing my story, that was 2 weeks ago. I tried to fix it but >>> didn't know how to read the error files listed below. (The only text >>> file is temp and it's gone now.) I also have other error files when I >>> run Everything and search for Agent, but I can't find them now. :-( >>> >>> Then last night, after restarting windows, but NOT s eeing any system >>> updates, the version on my laptop, the version I use every day, stopped >>> working. It too does nothing when I click on the task bar, except >>> write an error file >>> >>> I finally found on the web a post by Ralph that reminded me of the name >>> of the install file, so I reinstalled Agent 1.93 into the same >>> locations but no change. It's paid for and registered. >>> >>> Has something happened to Windows that might have affected both >>> computers. Can I remedy it. >>> >>> Right now I had to start using Xananews. I really didn't like Xananews. There was probably a way to stop it but every time I got headers it asked me questions, How many iirc & did I want bodies too. I've given up on version 1.93 and I'm migrating to version 4. I'll have big questions about that in a new thread. That post is more important to fixing things than this one. But I'm posting here to apologize. See further down. >>> ..... >>> HELP!!!! >>> >> >> >> I would use this first one. It installed just fine in a Win10 VM. >> These are from my collection (the collection gathered from questions). >> >> Name: a32en193__forte_free_agent_mirrors_easynews_com.exe >> Size: 2,405,565 bytes (2349 KiB) >> SHA256: B7CFF20A784D61968C7B297CE64B14B4C702623CE7B9DAF307D335DB87EB5FDD >> >> Name: a16en193__forte_free_agent_mirrors_easynews_com.exe >> Size: 2,548,809 bytes (2489 KiB) >> SHA256: 56EDBBD25B81F5A64C3A364F734AAE461E77EDA2136AD5E46F030BBB030EB34B >> >> ******* >> >> "The StackHash error occurs when DEP is invoked and has an issue with >> whatever application you’re trying to run (and there are several hundred >> out there that seem to give it fits). The error is related to >> Data Execution Prevention." >> >> "Exception 0xC000041D means that an unhandled exception was encountered >> during a user callback. It means that 0xC000041D is a second chance exception. >> So we should capture the first chance exception, if we want to know the root cause" >> >> And I think that might happen, if memory that is mapped as being for data, >> someone tries to execute it as program code. > > >According to the OP's other post , >both Agent 1.93 and Agent 4 are affected. I apologize Ralph and Paul and Paul for including version 4 in my first post. It was a complicated mistake***. When I decided the problem might be caused by windows and reposted to this group and the win10 group, I changed things but I didn't explicitly retract including version 4, and I should have. I did learn a lot about DEP however, and I assume that applies in a lot of places. *** I used to have 3 versions available on the desktop, two of 1.9 and one of 4, but when I went looking, there were only two icons and I assumed one was version 4 and when it wouldn't start, I thought version 4 wouldn't start. Later I saw that it was version 1.9 but it used a data directory, AgentFF , for Firefox I think. What could Firefox possibly have to do with Agen?. It's been less than 3 years but I can't remember. In addition, I foound a version of 1.93 I had called agent_original.exe . It's the same length, 2,917,408 as agent193's exe file but I can't remember what the difference is. It was a change made with a hex editor. Does anyone know what people changed in those days. BTW, I had major problems finding the install program for 1.93 was a32en193.exe. All there is ais an a, no agent like later versions. Beffore I saw this anser, on the web I found a post by Ralph from 13 years ago that gave its name. After that I reinstalled it but that didn't help. >Agent 1.93 is not compatible with DEP for applications. >But Agent 4 is compatible with DEP for applications. .....